Hi @KrasnoshchokBohdan. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@magento run all tests

@magento run all tests

@magento run all tests

@ihor-sviziev Hi, maybe you could help me with this? I don't know why but my latest pull requests don't have partner labels(

Hi @KrasnoshchokBohdan,

Adobe Commerce Engineering team started working on this issue. We will reach out to you if we need more information and you will get notified once the issue is fixed. Please leave comments for any further questions.

Thank you!

@engcom-Bravo
Hi! this is regarding issue or questions about partner labels?
Thanks!

Hi @KrasnoshchokBohdan,

This issue has been resolved under the internal Jira ticket AC-14494 by the internal team. According to the ticket, the fix is targeted for release in version 2.4.9-alpha1

Thanks.

@engcom-Bravo i don't see any commits mention AC-14494. Could you please point where to find them?

Hi @ihor-sviziev,

We got the reply from internal team "We have created the PR targeting the 2.4.9-alpha1-develop branch instead of 2.4-develop because the 2.4.9-alpha1 branch was established for the June release. Once the June release is finalized, the 2.4.9-alpha1 branch will be synced with 2.4-develop, and you will be able to see the commits reflected in the Magento2 repository"

Thanks.

@engcom-Bravo: that's just silly.

Can you at least then post the diff that fixed it in that invisible-to-the-community branch? Or are the changes exactly the same as proposed here in this PR?

Hi @hostep,

We got the reply Internal Team regarding git diff file with below screenshots

Thanks.